en	Quickly rebuild and install the plugin

en	When you do modification, you don't have to always rebuild the full project, and reinstall the plugin on your dev environment. You can build only the modified part (for example, if you only modified client files: `npm run build:client`). Check the `package.json` files for available build scripts.

en	When the plugin is already installed on your dev instance, and you haven't changed any dependency, you can quickly install your work by following these steps:

en	re-build necessary parts of the plugin (client, styles, ...),

en	overwrite the `data/plugins/node_modules/peertube-plugin-livechat/dist/` content of your dev instance by the content of the plugin's `dist` folder,

en	change recursively `plugins/node_modules/peertube-plugin-livechat/dist/` files owner to your `peertube` user,

en	restart your instance.
fr	Redémarrez vos services :

en	You need to add [DNS records](https://prosody.im/doc/dns) allowing remote servers to find "room.your_instance.tld" and "external.your_instance.tld" components.
fr	Vous devez ajouter un [enregistrement DNS](https://prosody.im/doc/dns) permettant aux serveurs distant de trouver le composant «room.votre_instance.tld».

en	The easiest way to do this is to add SRV records for the "room" and "external" [subdomain](https://prosody.im/doc/dns#subdomains):
fr	Le plus simple pour cela est d'ajouter un enregistrement SRV pour le [sous-domaine](https://prosody.im/doc/dns#subdomains) «room» :

en	record name: _xmpp-server._tcp.external.your_instance.tld. (replace «your_instance.tld» by your instance uri)
fr	nom de l'enregistrement : _xmpp-server._tcp.room.votre_instance.tld. (remplacez «votre_instance.tld» par la valeur adéquate)

en	Using the `dig` command to check your records, you should get a result similar to this:
fr	En utilisant la commande `dig` pour vérifier votre enregistrement, vous devriez obtenir un résultat similaire à celui-ci :

en	$ dig +short _xmpp-server._tcp.room.videos.john-livingston.fr. SRV 0 5 5269 videos.john-livingston.fr. $ dig +short _xmpp-server._tcp.external.videos.john-livingston.fr. SRV 0 5 5269 videos.john-livingston.fr.
fr	$ dig +short _xmpp-server._tcp.room.videos.john-livingston.fr. SRV 0 5 5269 videos.john-livingston.fr.

en	Plugin Peertube Livechat settings - External Authentication
fr	Paramètres du Plugin Peertube Livechat

en	External Authentication

en	Users that are not connected to your Peertube instance are joining the chat using "anonymous accounts" (they can freely choose a nickname, and will be assigned a random avatar).

en	You can enable some external authentication methods to allow user to create chat accounts. In such case their nickname and avatar will be automatically initialized with the remote account information.

en	Such "external account users" will be easier to moderate than anonymous accounts.

en	This also allows user to join the chat without creating Peertube account (in case your instance has closed registration for example, or without waiting for account approval).

en	![External login dialog - OpenID Connect](/peertube-plugin-livechat/images/external_login_dialog_oidc.png?classes=shadow,border&height=200px)
fr	![Fenêtre de dialogue connexion avec un compte externe](/peertube-plugin-livechat/images/external_login_dialog.png?classes=shadow,border&height=200px)

en	This page will describe available authentication methods.

en	For the user documentation, see [user documentation](/peertube-plugin-livechat/documentation/user/viewers/)
fr	Pour la documentation utilisateur⋅rice associé à ces fonctionnalités, veuillez vous référer à la page [de documentation utilisateur⋅rice](/peertube-plugin-livechat/fr/documentation/user/xmpp_clients/).

en	OpenID Connect

en	This feature is still experimental. This feature is available with the plugin version >= 9.0.0.
fr	Cette fonctionnalité arrive avec le plugin livechat version 9.0.0.

en	You can configure one external [OpenID Connect](https://openid.net/developers/how-connect-works/) compatible provider.

en	Doing so, you can for example use your website for Single Sign-On.

en	Popular CMS softwares (Wordpess, ...) offers plugins implementing OpenID Connect.

en	To enable this feature, first you have to create a client on your provider side (check the related documentation for enabling OpenID Connect). Then go to the [plugin settings](/peertube-plugin-livechat/documentation/admin/settings), and enable "{{% livechat_label external_auth_custom_oidc_label %}}".

en	Note: if you want to restrict allowed redirection urls on the provider side (best security practice), the plugin will show you the url to allow. Just copy it in your OpenID Connect application configuration.

en	You will now have to fill some settings.

en	This is the button label in the following screenshot:

en	For now, it is not possible to localize this label.
fr	Pour l'instant il n'est pas possible d'utiliser des tableaux Markdown : les outils de translation ne savent pas les gérer.

en	Your OpenID Connect provider must implement the [discovery URL](https://openid.net/specs/openid-connect-discovery-1_0.html). Just set here the discovery url, that should be something like `https://example.com/.well-known/openid-configuration`.

en	Note: if your provider use the standard `/.well-known/openid-configuration` path, you can omit it. For example `https://accounts.google.com` will work.

en	Your application Client ID.

en	You application Client secret.

en	Google, Facebook, ...

en	In addition to that, you can also configure one or several "standard" Open ID Connect provider (Google, Facebook, ...).

en	For these providers, discovery url and button label are preset. You just have to create an OAuth2 application on the provider side, and configure Client ID and Client Secret.

en	If you think of a standard provider that is not available, you can ask for implementation by [opening a new issue](/peertube-plugin-livechat/issues/).

en	If the button does not appear for end users, there might be a configuration issue. You can try the [diagnostic tool](/peertube-plugin-livechat/documentation/installation/troubleshooting/) to get more information.

en	Note: if you are connected to your Peertube account, the button will never show. So use a private browser window to test.

en	If the button is displayed but is not working, check your Peertube logs. It could be because the remote service does not use standard scopes or attribute names.

en	More to come
fr	Nouvelles fonctionnalités à venir...

en	Other authentication methods will be implemented in the future.

en	See the detailed documentation page:
fr	Voir la page de documentation dédiée à la documentation.

en	[External Authentication](/peertube-plugin-livechat/documentation/admin/external_auth/)
fr	[Le bot de tchat](/peertube-plugin-livechat/documentation/fr/user/streamers/bot)

en	Log in using an external authentication provider

en	The Peertube instance can configure external authentication providers (Mastodon accounts, Google accounts, ...). In such case, you will see a "{{% livechat_label login_using_external_account %}}" button, that will open a dialog modal. In this dialog modal, there will be some buttons to connect using a remote account.

en	Once you signed in the remote account, and have granted access, your nickname and avatar (if available) will be automatically fetched. No other data will be stored. These data will be automatically deleted several hours after your quit the chat.